Explanation of Change

The Claude PR reviewer dispatches a code-inline-reviewer subagent whose definition instructs it to Glob and Read all 28 coding-standards rule files on every run. Those reads land in the conversation (message) layer, beneath a per-checkout system prompt, so the ~25K-token ruleset is never a byte-stable, cacheable prefix: it is re-paid at the prompt-cache write rate on every PR run, and ~29 extra tool round-trips are spent just loading it.

This PR moves the ruleset into the subagent's system prompt so it becomes a deterministic, cacheable prefix:

• Adds .claude/skills/coding-standards/build-reviewer-agent.mjs — a deterministic compiler that embeds every rule file (sorted, checksummed, no timestamps) into the subagent definition. Same inputs produce byte-identical output, which is what prompt-cache prefix hits require.
• Adds .claude/skills/coding-standards/code-inline-reviewer.template.md — the source template. The only change vs. the previous agent definition is that the "load all rules" step is replaced by the embedded ruleset plus an injection marker; all other wording, the comment format, and the output schema are preserved byte-for-byte.
• Regenerates .claude/agents/code-inline-reviewer.md with all 28 rules embedded, so the subagent no longer Globs/Reads them at runtime.
• Updates .github/workflows/claude-review.yml: adds --exclude-dynamic-system-prompt-sections so per-run system-prompt sections (cwd, git state, OS) stop invalidating the prefix, and adds a CI step that runs the compiler with --check to fail fast if a rule file changes without regenerating the agent definition.

Net effect: the rule corpus is loaded once per run instead of via ~29 tool calls, and the now byte-stable prefix becomes eligible for cross-run prompt-cache reads (0.1x) instead of writes (1.25x) when runs fall within the cache TTL. Reviewer behavior is unchanged — the same rules are enforced.

Fixed Issues

$ #93665
PROPOSAL:

Tests

This change affects the CI reviewer tooling only — no app runtime or UI. To verify locally from the repo root:

1. Run node .claude/skills/coding-standards/build-reviewer-agent.mjs and verify it regenerates .claude/agents/code-inline-reviewer.md with all 28 rules embedded (a ### Rule index table with 28 rows and a closing </coding-standards> tag).
2. Run the build twice to separate files and confirm the output is byte-identical (deterministic): node .claude/skills/coding-standards/build-reviewer-agent.mjs --out /tmp/a.md && node .claude/skills/coding-standards/build-reviewer-agent.mjs --out /tmp/b.md && cmp /tmp/a.md /tmp/b.md.
3. Run node .claude/skills/coding-standards/build-reviewer-agent.mjs --check and verify it exits 0 when the committed agent definition is up to date.
4. Edit any file under .claude/skills/coding-standards/rules/, run --check again, and verify it exits non-zero (stale detected). Revert the edit.
5. Confirm .github/workflows/claude-review.yml is valid YAML and that the Run Claude Code (code) step's claude_args includes --exclude-dynamic-system-prompt-sections.

• Verify that no errors appear in the JS console

Offline tests

N/A — this change only affects CI reviewer tooling and does not touch network, API, or Onyx code.

QA Steps

N/A — CI/tooling change with no user-facing or staging-testable behavior. Title includes [No QA].

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos